cPanel Forums

I am preparing to upgrade to AlmaUnix froom CentOS 7 and when ruing the test I am getting the following 3 errors (ok 2 errors and 1 Waing) Here they are... * 06-11:28:12 (3425) [ERROR] 2 package(s) installed from unsupported YUM repo 'ul' from /etc/yum.repos.d/ul.repo * 06-11:28:12 (3425) [ERROR] 1 package(s) installed from unsupported YUM repo 'ul_webhostbox' from /etc/yum.repos.d/UL_webhostbox.repo * 06-11:28:12 (2638) [WARN] Unknown error while checking blockers: Wide... Click to expand... AlmaLinux Upgrade

I am always paranoid to make any serious changes that I don't totally understand on my server, so when I got a security advisory saying that: Apache vhosts are not segmented or chroot()ed. Enable “mod_ruid2” in the “EasyApache 4” area, enable “Jail Apache” in the “Tweak Settings” area, and change users to jailshell... Click to expand... switching from suphp to mod_ruid

Good moing, at the moment I have a problem with the renewal of the ssl certificate of the hostname of a server, the message is the following: The following cPanel service generated waings from the checkallsslcerts script. cpanel​ El sistema no pudo adquirir un certificado... 1 service generated waings while checking SSL certificates.

Cloudmak is killing my business, for the last 5 days Cloudmark has blocked my customers emails, I have requested remediation each day but no response nothing, what can I do? CSI IP Reputation Remediation Portal csi.cloudmark.com Remediation Already Requested A request for remediation has already been made for the IP address: 122.252.14.121. Only one request can be made per 24-hour period. I have checked MX Toolbox and I am not blacklisted anywhere else. I have the correct reverese... Cloudmark blacklisting my mail server

The Inteet, in its purest form, is a loosely coected graph of independent networks (also called Autonomous Systems (AS for short)). These networks use a signaling protocol called BGP (Border Gateway Protocol) to inform their neighbors (also known as peers) about the reachability of IP prefixes (a group of IP addresses) in and through their network. Part of this exchange contains useful metadata about the IP prefix that are used to inform network routing decisions. One example of the metadata is the full AS-path, which consists of the different autonomous systems an IP packet needs to pass through to reach its destination.As we all want our packets to get to their destination as fast as possible, selecting the shortest AS-path for a given prefix is a good idea. This is where something called prepending comes into play.Routing on the Inteet, a primerLet's briefly talk about how the Inteet works at its most fundamental level, before we dive into some nitty-gritty details.The Inteet is, at its core, a massively intercoected network of thousands of networks. Each network owns two things that are critical:1. An Autonomous System Number (ASN): a 32-bit integer that uniquely identifies a network. For example, one of the Cloudflare ASNs (we have multiple) is 13335.2. IP prefixes: An IP prefix is a range of IP addresses, bundled together in powers of two: In the IPv4 space, two addresses form a /31 prefix, four form a /30, and so on, all the way up to /0, which is shorthand

A lot of Cloudflare's technology is well documented. For example, how we handle traffic between the eyeballs (clients) and our servers has been discussed many times on this blog: “A brief primer on anycast (2011)”, "Load Balancing without Load Balancers (2013)", "Path MTU discovery in practice (2015)", "Cloudflare's edge load balancer (2020)", "How we fixed the BSD socket API (2022)".However, we have rarely talked about the second part of our networking setup — how our servers fetch the content from the Inteet. In this blog we’re going to cover this gap. We'll discuss how we manage Cloudflare IP addresses used to retrieve the data from the Inteet, how our egress network design has evolved and how we optimized it for best use of available IP space.Brace yourself. We have a lot to cover.Terminology first!Each Cloudflare server deals with many kinds of networking traffic, but two rough categories stand out:Inteet sourced traffic - Inbound coections initiated by eyeball to our servers. In the context of this blog post we'll call these "ingress coections".Cloudflare sourced traffic - Outgoing coections initiated by our servers to other hosts on the Inteet. For brevity, we'll call these "egress coections".The egress part, while rarely discussed on this blog, is critical for our operation. Our servers must initiate outgoing coections to get their jobs done! Like:In our CDN product, before the content is cached, it's fetched from the origin servers. See "Pingora, t

"The more you practice the art of thankfulness, the more you have to be thankful for." — Norman Vincent Peale, American authorThe turkey. The sweet potatoes. The stuffing. The pumpkin pie. Yesterday, November 24, 2022, was Thanksgiving Day in the US. A time for families and loved ones to be together and thankful, according to the tradition. Last year, we saw how the US paused shopping (and browsing) for Thanksgiving. So, how was it this year? Not only did we see Inteet traffic go down (by 13%) during Thanksgiving dier, but it was much higher than usual the day before and the day after (the Black Friday effect… so far). There was also a clear, but short, Thanksgiving Day effect on e-commerce DNS trends. We'll have to wait to see what Black Friday looks like.Let’s start with Inteet traffic at the time of Thanksgiving dier. Although every family is different, a 2018 survey of US consumers showed that for 42% early afteoon (between 13:00 and 15:00 is the preferred time to sit at the table and start to dig in). But 16:00 seems to be the “correct time” — The Atlantic explains why. That said, Cloudflare Radar shows that between 21:00 and 01:00 UTC (we use that as the standard timezone in Radar) there was a clear drop in Inteet traffic, mostly between 21:00 and 22:00 UTC, when traffic dropped 13%, compared with the week before. That time period is “translated” for the East Coast to between 16:00 and 20:00 EST and for the West Coast the time between 13:00 to 17:00 PST. Sim

We want our digital data to be safe. We want to visit websites, send bank details, type passwords, sign documents online, login into remote computers, encrypt data before storing it in databases and be sure that nobody can tamper with it. Cryptography can provide a high degree of data security, but we need to protect cryptographic keys.At the same time, we can’t have our key written somewhere securely and just access it occasionally. Quite the opposite, it’s involved in every request where we do crypto-operations. If a site supports TLS, then the private key is used to establish each coection.Unfortunately cryptographic keys sometimes leak and when it happens, it is a big problem. Many leaks happen because of software bugs and security vulnerabilities. In this post we will lea how the Linux keel can help protect cryptographic keys from a whole class of potential security vulnerabilities: memory access violations.Memory access violationsAccording to the NSA, around 70% of vulnerabilities in both Microsoft's and Google's code were related to memory safety issues. One of the consequences of incorrect memory accesses is leaking security data (including cryptographic keys). Cryptographic keys are just some (mostly random) data stored in memory, so they may be subject to memory leaks like any other in-memory data. The below example shows how a cryptographic key may accidentally leak via stack memory reuse:broken.c#include <stdio.h> #include <stdint.h> static void

This post is also available in 简体中文. IT teams have historically faced challenges with performance, security, and reliability for employees and network resources in mainland China. Today, along with our strategic partners, we’re excited to aounce expansion of our Cloudflare One product suite to tackle these problems, with the goal of creating the best SASE experience for users and organizations in China.Cloudflare One, our comprehensive SASE platform, allows organizations to coect any source or destination and apply single-pass security policies from one unified control plane. Cloudflare One is built on our global network, which spans 275 cities across the globe and is within 50ms of 95% of the world’s Inteet-coected population. Our ability to serve users extremely close to wherever they’re working—whether that’s in a corporate office, their home, or a coffee shop—has been a key reason customers choose our platform since day one.In 2015, we extended our Application Services portfolio to cities in mainland China; in 2020, we expanded these capabilities to offer better performance and security through our strategic partnership with JD Cloud. Today, we’re unveiling our latest steps in this jouey: extending the capabilities of Cloudflare One to users and organizations in mainland China, through additional strategic partnerships. Let’s break down a few ways you can achieve better coectivity, security, and performance for your China network and users with Cloudflare One.

This post is also available in 繁體中文, 简体中文, 日本語, 한국어, Deutsch, Français, Italiano, Pусский, Español, Português. Cloudflare is raising prices for the first time in the last 12 years. Begiing January 15, 2023, new sign-ups will be charged $25 per month for our Pro Plan (up from $20 per month) and $250 per month for our Business Plan (up from $200 per month). Any paying customers who sign up before January 15, 2023, including any currently paying customers who signed up at any point over the last 12 years, will stay at the old monthly price until May 14, 2023.We are also introducing an option to pay aually, rather than monthly, that we hope most customers will choose to switch to. Aual plans are available today and discounted from the new monthly rate to $240 per year for the Pro Plan (the equivalent of $20 per month, saving $60 per year) and $2,400 per year for the Business Plan (the equivalent of $200 per month, saving $600 per year). In other words, if you choose to pay aually for Cloudflare you can lock in our old monthly prices.After not raising prices in our history, this was something we thought carefully about before deciding to do. While we have over a decade of network expansion and iovation under our belts, what may not be intuitive is that our goal is not to increase revenue from this change. We need to invest up front in building out our network, and the main reason we're making this change is to more closely map our business with the timing of ou